Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d0ff310eb8765b52cf2003c028de839234d7d2131517a0f2b9c4d3bbb5e05af

Tx prefix hash: 4383a48d218092ff7f69a864b4bd5c5741183a535600ae15c97d8e4736d0bf48
Tx public key: b8a2b634511fc43612dd3cc4e83265ed81c7e158cc69dce78aef2b8e263936f9
Timestamp: 1706324324 Timestamp [UCT]: 2024-01-27 02:58:44 Age [y:d:h:m:s]: 01:068:18:44:45
Block: 944149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310243 RingCT/type: yes/0
Extra: 01b8a2b634511fc43612dd3cc4e83265ed81c7e158cc69dce78aef2b8e263936f902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbf41695c8db9ac64ecd3e44f9407b5f88c653c1a9573e4a648564d6f1049983 0.600000000000 1402379 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": 944159, "vin": [ { "gen": { "height": 944149 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbf41695c8db9ac64ecd3e44f9407b5f88c653c1a9573e4a648564d6f1049983" } } ], "extra": [ 1, 184, 162, 182, 52, 81, 31, 196, 54, 18, 221, 60, 196, 232, 50, 101, 237, 129, 199, 225, 88, 204, 105, 220, 231, 138, 239, 43, 142, 38, 57, 54, 249, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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