Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d00d5ae127d46f571ccaf907786733cae534f5165e285a354313b86fa97a1d00

Tx prefix hash: 366548614376f5c6dde68f3c2904d4bbbe9cad9fbc349b43322d35db505c95b8
Tx public key: 5c489a5efc54a7bcc15c8ad1c060b379018d08b6dff56b25d8d31c1ad748be02
Timestamp: 1702984412 Timestamp [UCT]: 2023-12-19 11:13:32 Age [y:d:h:m:s]: 01:149:09:02:20
Block: 916498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367899 RingCT/type: yes/0
Extra: 015c489a5efc54a7bcc15c8ad1c060b379018d08b6dff56b25d8d31c1ad748be0202110000002d75e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbb91237b095669619fea039f89822e263b4084841a7b920b2a1b19e2aa13cdc 0.600000000000 1374050 of 15

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": 916508, "vin": [ { "gen": { "height": 916498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbb91237b095669619fea039f89822e263b4084841a7b920b2a1b19e2aa13cdc" } } ], "extra": [ 1, 92, 72, 154, 94, 252, 84, 167, 188, 193, 92, 138, 209, 192, 96, 179, 121, 1, 141, 8, 182, 223, 245, 107, 37, 216, 211, 28, 26, 215, 72, 190, 2, 2, 17, 0, 0, 0, 45, 117, 227, 240, 233, 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