Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19e9f143bd54a75c573d891294476e25b54da1148dcaa0e37ad9c3dbf2d4d146

Tx prefix hash: 322428a3fca5adf1549f423c83778a77eebe462e6ce252c6c3ccf4705f30b7a4
Tx public key: 8710717bfbaef6ecb957e11ae98f84a3690e9787e5e2d3688673e25ce2ef0a18
Timestamp: 1731483169 Timestamp [UCT]: 2024-11-13 07:32:49 Age [y:d:h:m:s]: 00:359:21:29:39
Block: 1152656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254772 RingCT/type: yes/0
Extra: 018710717bfbaef6ecb957e11ae98f84a3690e9787e5e2d3688673e25ce2ef0a180211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f14b56d16e99686a9b5964c9fc3245e2fb31b3258bc4f3af39a1c365f0447de4 0.600000000000 1638259 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": 1152666, "vin": [ { "gen": { "height": 1152656 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f14b56d16e99686a9b5964c9fc3245e2fb31b3258bc4f3af39a1c365f0447de4" } } ], "extra": [ 1, 135, 16, 113, 123, 251, 174, 246, 236, 185, 87, 225, 26, 233, 143, 132, 163, 105, 14, 151, 135, 229, 226, 211, 104, 134, 115, 226, 92, 226, 239, 10, 24, 2, 17, 0, 0, 0, 3, 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