Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 384dd6f38eba65c109fb8cbfcf38c986fc1dfb292b7685063ee0699b6e491c47

Tx prefix hash: 5a739d11e43c55fb595da7a27a198e8817e8d16d523157da6ed7f54c26de10b3
Tx public key: 4b9bc3a329e3b7387409322db1aa27e356e8337d89eaef5c8909539b3d93c3f1
Timestamp: 1740940806 Timestamp [UCT]: 2025-03-02 18:40:06 Age [y:d:h:m:s]: 00:263:09:47:58
Block: 1230705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185995 RingCT/type: yes/0
Extra: 014b9bc3a329e3b7387409322db1aa27e356e8337d89eaef5c8909539b3d93c3f10211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f37c34185954e6d664af93cc2fca9427ed45e7ce101b90b9081bd269d46e1965 0.600000000000 1717604 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": 1230715, "vin": [ { "gen": { "height": 1230705 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f37c34185954e6d664af93cc2fca9427ed45e7ce101b90b9081bd269d46e1965" } } ], "extra": [ 1, 75, 155, 195, 163, 41, 227, 183, 56, 116, 9, 50, 45, 177, 170, 39, 227, 86, 232, 51, 125, 137, 234, 239, 92, 137, 9, 83, 155, 61, 147, 195, 241, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 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