Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 645bed1fc322d6a5631d57d8306810e826a639e16add2eaaa288335b5171892c

Tx prefix hash: f70684bad91259b6cc725082212a90f27359f8c0aa4cadf9050c51bf5a8c6a44
Tx public key: 73074948c6ab0fb5a9e21ce9ff29910222c848437cc527f53cb4a7523eb9d4f4
Timestamp: 1758034211 Timestamp [UCT]: 2025-09-16 14:50:11 Age [y:d:h:m:s]: 00:058:00:58:43
Block: 1369772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41551 RingCT/type: yes/0
Extra: 0173074948c6ab0fb5a9e21ce9ff29910222c848437cc527f53cb4a7523eb9d4f4021100000004b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ef5b02a590a14c1e9604f39c547686e659310638f5d80c1f7b315d419699335 0.600000000000 1857847 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": 1369782, "vin": [ { "gen": { "height": 1369772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ef5b02a590a14c1e9604f39c547686e659310638f5d80c1f7b315d419699335" } } ], "extra": [ 1, 115, 7, 73, 72, 198, 171, 15, 181, 169, 226, 28, 233, 255, 41, 145, 2, 34, 200, 72, 67, 124, 197, 39, 245, 60, 180, 167, 82, 62, 185, 212, 244, 2, 17, 0, 0, 0, 4, 178, 247, 132, 196, 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