Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daf6d9a7be85523d5f3d69e94ddf4197309bd629a4640ff829914aa625ed0f3e

Tx prefix hash: 009e628cc5214badbe3eed6355e74d25d99abcb11540d83890d78d8d326d5d73
Tx public key: 5789b8e7b2e68a02898cfa5e392bc636d551d17d7a3c2bc16a212eb08fec1b20
Timestamp: 1745870453 Timestamp [UCT]: 2025-04-28 20:00:53 Age [y:d:h:m:s]: 00:162:11:49:09
Block: 1271523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113782 RingCT/type: yes/0
Extra: 015789b8e7b2e68a02898cfa5e392bc636d551d17d7a3c2bc16a212eb08fec1b200211000000059f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 878e6adb6d87ae595a1a8ef8ec6f58744b8032f33b29b86785b97b8a65efd37c 0.600000000000 1758786 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": 1271533, "vin": [ { "gen": { "height": 1271523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "878e6adb6d87ae595a1a8ef8ec6f58744b8032f33b29b86785b97b8a65efd37c" } } ], "extra": [ 1, 87, 137, 184, 231, 178, 230, 138, 2, 137, 140, 250, 94, 57, 43, 198, 54, 213, 81, 209, 125, 122, 60, 43, 193, 106, 33, 46, 176, 143, 236, 27, 32, 2, 17, 0, 0, 0, 5, 159, 159, 230, 140, 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