Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d34213d768b2b8a2c39e28d99af540c6debc55eb7b7dfb2bff62cf842c88611a

Tx prefix hash: 7e057f314eff4bd2f934ef54345c082b67293a41efa801d839bb4d3327dfed13
Tx public key: 0dfbe3a0f74a2f488b950a7185ae3f6344041f794f5638a76ac239cf546aec3b
Timestamp: 1712782298 Timestamp [UCT]: 2024-04-10 20:51:38 Age [y:d:h:m:s]: 01:209:04:59:15
Block: 997696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408185 RingCT/type: yes/0
Extra: 010dfbe3a0f74a2f488b950a7185ae3f6344041f794f5638a76ac239cf546aec3b0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 089946a242a5fa3914ddb7138d475b6bf363b6487671e95b49d3cd02c1e65a95 0.600000000000 1458130 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": 997706, "vin": [ { "gen": { "height": 997696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "089946a242a5fa3914ddb7138d475b6bf363b6487671e95b49d3cd02c1e65a95" } } ], "extra": [ 1, 13, 251, 227, 160, 247, 74, 47, 72, 139, 149, 10, 113, 133, 174, 63, 99, 68, 4, 31, 121, 79, 86, 56, 167, 106, 194, 57, 207, 84, 106, 236, 59, 2, 17, 0, 0, 0, 3, 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