Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f5781dc453b76fdd2457cc625f2f66396c02bf73c172a03c8c7ebbcc6352ec1

Tx prefix hash: 805e98dce2ee4e69cbe6f2fc1a2556c9d9cb10e5bdc9950fa720651b1754f795
Tx public key: cd71d27f2f09602286e28389ecea49c1d1d71972466c0feea0bb6e631e87875d
Timestamp: 1624988283 Timestamp [UCT]: 2021-06-29 17:38:03 Age [y:d:h:m:s]: 03:256:17:55:09
Block: 285386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 952276 RingCT/type: yes/0
Extra: 01cd71d27f2f09602286e28389ecea49c1d1d71972466c0feea0bb6e631e87875d0211000000bab8178fc1000000000000000000

1 output(s) for total of 69.569800908000 dcy

stealth address amount amount idx
00: 8bb0b5a0c350163d814d1294a1dc43372029468cff068c693abbf126b5d112f2 69.569800908000 597517 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": 285396, "vin": [ { "gen": { "height": 285386 } } ], "vout": [ { "amount": 69569800908, "target": { "key": "8bb0b5a0c350163d814d1294a1dc43372029468cff068c693abbf126b5d112f2" } } ], "extra": [ 1, 205, 113, 210, 127, 47, 9, 96, 34, 134, 226, 131, 137, 236, 234, 73, 193, 209, 215, 25, 114, 70, 108, 15, 238, 160, 187, 110, 99, 30, 135, 135, 93, 2, 17, 0, 0, 0, 186, 184, 23, 143, 193, 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