Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 78c3bb4487781f87a8a27476e949082d46cd3abfe63fb66607e290be2a188814

Tx prefix hash: a56c52a3106d2a45b91d472d13760aab19a7dbe2a38e845592150ee718af74fc
Tx public key: 5ee4ed5279bc298c9c619f8c17abc3faaf44b59bbaa5d9f9f3d22f7313837af8
Timestamp: 1581112084 Timestamp [UCT]: 2020-02-07 21:48:04 Age [y:d:h:m:s]: 04:321:15:01:27
Block: 60779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121392 RingCT/type: yes/0
Extra: 015ee4ed5279bc298c9c619f8c17abc3faaf44b59bbaa5d9f9f3d22f7313837af80211000000194ac5aa02000000000000000000

1 output(s) for total of 386.031072676000 dcy

stealth address amount amount idx
00: 3436ef0d2cf592321304fe98fa10de6c8d2575a598355c9a5175856a24f0704e 386.031072676000 111934 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 60789, "vin": [ { "gen": { "height": 60779 } } ], "vout": [ { "amount": 386031072676, "target": { "key": "3436ef0d2cf592321304fe98fa10de6c8d2575a598355c9a5175856a24f0704e" } } ], "extra": [ 1, 94, 228, 237, 82, 121, 188, 41, 140, 156, 97, 159, 140, 23, 171, 195, 250, 175, 68, 181, 155, 186, 165, 217, 249, 243, 210, 47, 115, 19, 131, 122, 248, 2, 17, 0, 0, 0, 25, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8