Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 609168f41202118b1d6954b9f8700cc6a65f2bf7a05c5c629fe476a88c8b2b9a

Tx prefix hash: 8f43fd3a0d56d51ae128c9f738653f874d4a710c6fe23675d0022135baae8e16
Tx public key: b17a5a6852ea81b27e021fa6225f5b721a281fb489bbe37aa25c0cdb31df4cb8
Timestamp: 1731592807 Timestamp [UCT]: 2024-11-14 14:00:07 Age [y:d:h:m:s]: 01:002:11:08:38
Block: 1153571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260175 RingCT/type: yes/0
Extra: 01b17a5a6852ea81b27e021fa6225f5b721a281fb489bbe37aa25c0cdb31df4cb8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfd95a522614aedaa692707e5e9f53b7017c78dfc1e8da13e70ecb08573169c4 0.600000000000 1639180 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": 1153581, "vin": [ { "gen": { "height": 1153571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfd95a522614aedaa692707e5e9f53b7017c78dfc1e8da13e70ecb08573169c4" } } ], "extra": [ 1, 177, 122, 90, 104, 82, 234, 129, 178, 126, 2, 31, 166, 34, 95, 91, 114, 26, 40, 31, 180, 137, 187, 227, 122, 162, 92, 12, 219, 49, 223, 76, 184, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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