Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3458e676f130d81abe7f641d32dfb8d12927ca853c9be0ce763a721e1508257e

Tx prefix hash: f56e0d968d1aef21faafb9cc5c75fdae0ae88e968a01b6a2af1a5de345eabebf
Tx public key: 090bf204d35ea792d3d1b7bdcb41aa4d05f75577df304dc5ee4f89a3803c2f3d
Timestamp: 1741293137 Timestamp [UCT]: 2025-03-06 20:32:17 Age [y:d:h:m:s]: 00:259:17:36:37
Block: 1233620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183375 RingCT/type: yes/0
Extra: 01090bf204d35ea792d3d1b7bdcb41aa4d05f75577df304dc5ee4f89a3803c2f3d021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef995a7cc31f5f9bcbb7b4b6a702c9acd6fa9ca8f4d63c986018baefed58f8e4 0.600000000000 1720543 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": 1233630, "vin": [ { "gen": { "height": 1233620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef995a7cc31f5f9bcbb7b4b6a702c9acd6fa9ca8f4d63c986018baefed58f8e4" } } ], "extra": [ 1, 9, 11, 242, 4, 211, 94, 167, 146, 211, 209, 183, 189, 203, 65, 170, 77, 5, 247, 85, 119, 223, 48, 77, 197, 238, 79, 137, 163, 128, 60, 47, 61, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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