Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a4d5b9da6707dfd317aceee3d1bc8a6bf4fcfa0cbf6101b763a988ff7eff1a8

Tx prefix hash: e1e4b5eb42ca960b74d3a48314e56358ce7570ab661a1e173b8a2272b1c70e20
Tx public key: 47a3f7c376974d94210679280067e3a6cb75f811e9ab926a324f812dee30420e
Timestamp: 1704135611 Timestamp [UCT]: 2024-01-01 19:00:11 Age [y:d:h:m:s]: 01:094:07:03:10
Block: 926026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328498 RingCT/type: yes/0
Extra: 0147a3f7c376974d94210679280067e3a6cb75f811e9ab926a324f812dee30420e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a44b4660ef8cac9f39e2e94375d6ea72f784ddca42b1a4bf45311decb8fea1a1 0.600000000000 1383796 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": 926036, "vin": [ { "gen": { "height": 926026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a44b4660ef8cac9f39e2e94375d6ea72f784ddca42b1a4bf45311decb8fea1a1" } } ], "extra": [ 1, 71, 163, 247, 195, 118, 151, 77, 148, 33, 6, 121, 40, 0, 103, 227, 166, 203, 117, 248, 17, 233, 171, 146, 106, 50, 79, 129, 45, 238, 48, 66, 14, 2, 17, 0, 0, 0, 2, 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