Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e309df6caf70ad7021dc1c98495b9076037095adbca3e51175ec101d80b9394f

Tx prefix hash: baa3d11a78fa164d102ff0e3cd8510ce221d14b225c90e444aa3a27500fd0097
Tx public key: 6a8969f0831f45122239f99f8e38df63f0aa5f0490cb46cf443c19e83e305a8a
Timestamp: 1713844753 Timestamp [UCT]: 2024-04-23 03:59:13 Age [y:d:h:m:s]: 00:308:08:22:34
Block: 1006526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220398 RingCT/type: yes/0
Extra: 016a8969f0831f45122239f99f8e38df63f0aa5f0490cb46cf443c19e83e305a8a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e763858b07c3680c4fd5d8b74fd15a5eec8c20988b0e997d88d6d7bf332c93c3 0.600000000000 1467584 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": 1006536, "vin": [ { "gen": { "height": 1006526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e763858b07c3680c4fd5d8b74fd15a5eec8c20988b0e997d88d6d7bf332c93c3" } } ], "extra": [ 1, 106, 137, 105, 240, 131, 31, 69, 18, 34, 57, 249, 159, 142, 56, 223, 99, 240, 170, 95, 4, 144, 203, 70, 207, 68, 60, 25, 232, 62, 48, 90, 138, 2, 17, 0, 0, 0, 1, 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