Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f8668bd9643f2d33a3802ef4f314e3b19a50fe915296fc17bdf9325728e104d

Tx prefix hash: 268205f59fc67b74333caf9aeb8e62ec02d1ce7bd307257d0e76ad152b0fad8c
Tx public key: 7a8b81a110cd02265e9b62349da167465da2e7f2555ec65ddc6c78e0538d0730
Timestamp: 1635969953 Timestamp [UCT]: 2021-11-03 20:05:53 Age [y:d:h:m:s]: 03:177:03:20:50
Block: 366690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 904936 RingCT/type: yes/0
Extra: 017a8b81a110cd02265e9b62349da167465da2e7f2555ec65ddc6c78e0538d073002110000000d1154028c000000000000000000

1 output(s) for total of 37.411421391000 dcy

stealth address amount amount idx
00: f7a2b3e74ec909fc19f0ef1cf2d9edaa9dd9967686ee23b3ced9e2bfc42d1e7c 37.411421391000 744276 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": 366700, "vin": [ { "gen": { "height": 366690 } } ], "vout": [ { "amount": 37411421391, "target": { "key": "f7a2b3e74ec909fc19f0ef1cf2d9edaa9dd9967686ee23b3ced9e2bfc42d1e7c" } } ], "extra": [ 1, 122, 139, 129, 161, 16, 205, 2, 38, 94, 155, 98, 52, 157, 161, 103, 70, 93, 162, 231, 242, 85, 94, 198, 93, 220, 108, 120, 224, 83, 141, 7, 48, 2, 17, 0, 0, 0, 13, 17, 84, 2, 140, 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