Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35c336df732fc4f51cba49b672eb3f79f91e29d0eaba088349eae5db1813bc59

Tx prefix hash: 1fc1efae273270737bc2233851df3e46fc4c41e47d424bc2e0acc1b239ccb8fb
Tx public key: 78d9c98b1089dd0076ff64e0e7eba14f89d6a6601a3f5cb9221ec75f37a315e7
Timestamp: 1711246034 Timestamp [UCT]: 2024-03-24 02:07:14 Age [y:d:h:m:s]: 01:231:05:24:43
Block: 985006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 423930 RingCT/type: yes/0
Extra: 0178d9c98b1089dd0076ff64e0e7eba14f89d6a6601a3f5cb9221ec75f37a315e70211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 811ee0d50fb3bb7db6e92d416f08aeb1db35f02f7ab17d0cc2eea8e569f47a21 0.600000000000 1445211 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": 985016, "vin": [ { "gen": { "height": 985006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "811ee0d50fb3bb7db6e92d416f08aeb1db35f02f7ab17d0cc2eea8e569f47a21" } } ], "extra": [ 1, 120, 217, 201, 139, 16, 137, 221, 0, 118, 255, 100, 224, 231, 235, 161, 79, 137, 214, 166, 96, 26, 63, 92, 185, 34, 30, 199, 95, 55, 163, 21, 231, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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