Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7ca63bf821d942e03ee4fda8f3d537d3b67886b7d51ab17fcaa56a523237260

Tx prefix hash: 5c94708a7124fd01e26208ab40bd2e1aa028eb7b3f4d00c303e1efdb49a83468
Tx public key: ad13d5d579cb89ab93a79a6637377bc3b73330baa8e5ca06bb4c92b80b16284e
Timestamp: 1720815494 Timestamp [UCT]: 2024-07-12 20:18:14 Age [y:d:h:m:s]: 00:244:10:53:24
Block: 1064329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174626 RingCT/type: yes/0
Extra: 01ad13d5d579cb89ab93a79a6637377bc3b73330baa8e5ca06bb4c92b80b16284e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23a264f8b43983e58f68797295315aa23d7202f63b77772b6b4cb15b9d8f9193 0.600000000000 1534854 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": 1064339, "vin": [ { "gen": { "height": 1064329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23a264f8b43983e58f68797295315aa23d7202f63b77772b6b4cb15b9d8f9193" } } ], "extra": [ 1, 173, 19, 213, 213, 121, 203, 137, 171, 147, 167, 154, 102, 55, 55, 123, 195, 183, 51, 48, 186, 168, 229, 202, 6, 187, 76, 146, 184, 11, 22, 40, 78, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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