Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 457bf34878575cd8c1ae2df56f083f5f1b57c40ed0efc2e13b8053a29d035710

Tx prefix hash: 2da0772079fa834a769da1ad1b29ddcad90db6172768ddb8994c02f00df0aef7
Tx public key: fede075649a2388b0f494209bb06b4da2e112775c1a5b6fd891e1c989dd57c33
Timestamp: 1749417197 Timestamp [UCT]: 2025-06-08 21:13:17 Age [y:d:h:m:s]: 00:158:10:31:48
Block: 1300884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110925 RingCT/type: yes/0
Extra: 01fede075649a2388b0f494209bb06b4da2e112775c1a5b6fd891e1c989dd57c3302110000000243846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43bba3b0e8f0aa8a6a391a81d4b9c678dd3a3ebaef3c1105e040a58bbf2effef 0.600000000000 1788437 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": 1300894, "vin": [ { "gen": { "height": 1300884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43bba3b0e8f0aa8a6a391a81d4b9c678dd3a3ebaef3c1105e040a58bbf2effef" } } ], "extra": [ 1, 254, 222, 7, 86, 73, 162, 56, 139, 15, 73, 66, 9, 187, 6, 180, 218, 46, 17, 39, 117, 193, 165, 182, 253, 137, 30, 28, 152, 157, 213, 124, 51, 2, 17, 0, 0, 0, 2, 67, 132, 109, 102, 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