Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d93f1abc2fb3dd1a5e6d8e12f2344010145e2a2204ee56e21d44a56681ea1595

Tx prefix hash: f1961d8be21f16be5c641d4ddd868d84b63be499a62edc5939c612fa2620eeb6
Tx public key: f08f5d175fd13b51cce7a51e8fac5c0ee4a37760ac98b30daa942d543521d6e2
Timestamp: 1744311891 Timestamp [UCT]: 2025-04-10 19:04:51 Age [y:d:h:m:s]: 00:256:18:40:47
Block: 1258607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181282 RingCT/type: yes/0
Extra: 01f08f5d175fd13b51cce7a51e8fac5c0ee4a37760ac98b30daa942d543521d6e20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab3546f037090fdb3068ff8fdca5d9c1bdd3bf9243b7f87a141aa500ba010e98 0.600000000000 1745744 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": 1258617, "vin": [ { "gen": { "height": 1258607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab3546f037090fdb3068ff8fdca5d9c1bdd3bf9243b7f87a141aa500ba010e98" } } ], "extra": [ 1, 240, 143, 93, 23, 95, 209, 59, 81, 204, 231, 165, 30, 143, 172, 92, 14, 228, 163, 119, 96, 172, 152, 179, 13, 170, 148, 45, 84, 53, 33, 214, 226, 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