Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76d22b4cf785f48fdd0f8b1f70a10d7f7b3d08d207d010058b4e1ff62b656e0b

Tx prefix hash: b48c6a0fcfaa35b7abf9c7707ede0e86b2bb7ba999e3f8b3fe22d1256b624531
Tx public key: 6850e8db431950e3f05ef650da8744183b62009eacf942f0a245e606c432019c
Timestamp: 1696138913 Timestamp [UCT]: 2023-10-01 05:41:53 Age [y:d:h:m:s]: 01:187:00:01:44
Block: 859939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394698 RingCT/type: yes/0
Extra: 016850e8db431950e3f05ef650da8744183b62009eacf942f0a245e606c432019c02110000000233af99f4000000000000000000

1 output(s) for total of 0.868290716000 dcy

stealth address amount amount idx
00: 593770dc8a048bc1b3fdc77a8617a438815ffb396a9a0314d112879f874dbfd8 0.868290716000 1314195 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": 859949, "vin": [ { "gen": { "height": 859939 } } ], "vout": [ { "amount": 868290716, "target": { "key": "593770dc8a048bc1b3fdc77a8617a438815ffb396a9a0314d112879f874dbfd8" } } ], "extra": [ 1, 104, 80, 232, 219, 67, 25, 80, 227, 240, 94, 246, 80, 218, 135, 68, 24, 59, 98, 0, 158, 172, 249, 66, 240, 162, 69, 230, 6, 196, 50, 1, 156, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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