Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd8c91a1c5a25567dd85cf85fa9998d77b6b1a910d60b5c9055e5b1d5ee2d293

Tx prefix hash: f4fc8cb4ce4afb9616a1654c7a1e1ccce8efc72afe542fcc82e6daf925657708
Tx public key: 6a454d5463ac0e3eea2d4dcfb2e4cb6ac775a6f329b167444663eca5411b2c70
Timestamp: 1750443688 Timestamp [UCT]: 2025-06-20 18:21:28 Age [y:d:h:m:s]: 00:153:08:48:25
Block: 1309217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107445 RingCT/type: yes/0
Extra: 016a454d5463ac0e3eea2d4dcfb2e4cb6ac775a6f329b167444663eca5411b2c700211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8446a2c3e99a78a40dc9ec85c73ffa6351a2520099d2725f73b400f633a2d6d8 0.600000000000 1796832 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": 1309227, "vin": [ { "gen": { "height": 1309217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8446a2c3e99a78a40dc9ec85c73ffa6351a2520099d2725f73b400f633a2d6d8" } } ], "extra": [ 1, 106, 69, 77, 84, 99, 172, 14, 62, 234, 45, 77, 207, 178, 228, 203, 106, 199, 117, 166, 243, 41, 177, 103, 68, 70, 99, 236, 165, 65, 27, 44, 112, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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