Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d85e2d62561914ec87b4cbf9708ee7db4e07ccc56a91bacdd938d645926083ec

Tx prefix hash: a4276293f8620d29dcecb46801650bb51e57c29f4ba1d214b566048e4257c835
Tx public key: 60b0cb1c6025bc6b9851842ce308783c0cf8a8603d9bf6b5f720084f8a4d0e3c
Timestamp: 1725968169 Timestamp [UCT]: 2024-09-10 11:36:09 Age [y:d:h:m:s]: 00:256:07:27:58
Block: 1107038 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183046 RingCT/type: yes/0
Extra: 0160b0cb1c6025bc6b9851842ce308783c0cf8a8603d9bf6b5f720084f8a4d0e3c02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1069e99219bec629aa75d07373179485386c5ff0cfbd284e233a8cb9564ff0b4 0.600000000000 1584645 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": 1107048, "vin": [ { "gen": { "height": 1107038 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1069e99219bec629aa75d07373179485386c5ff0cfbd284e233a8cb9564ff0b4" } } ], "extra": [ 1, 96, 176, 203, 28, 96, 37, 188, 107, 152, 81, 132, 44, 227, 8, 120, 60, 12, 248, 168, 96, 61, 155, 246, 181, 247, 32, 8, 79, 138, 77, 14, 60, 2, 17, 0, 0, 0, 6, 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