Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8b6050a250ce4f4168c09aa6345f601b3bee2b5eb6f3df10265a5dfbf4c6922

Tx prefix hash: 9fdb12242a18debe721d9cf5616fb0118ede006174806504e91146329a9b4101
Tx public key: 2b6e116032e59fe1ee2bfa493e15eea854d4fd43258c03fd44e9c8cdd4918db1
Timestamp: 1731008844 Timestamp [UCT]: 2024-11-07 19:47:24 Age [y:d:h:m:s]: 00:016:22:53:24
Block: 1148737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12132 RingCT/type: yes/0
Extra: 012b6e116032e59fe1ee2bfa493e15eea854d4fd43258c03fd44e9c8cdd4918db10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1608af49b5814b7dbe02bdfb30312169fc5c5eda829449752a8c126b31374edc 0.600000000000 1633656 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": 1148747, "vin": [ { "gen": { "height": 1148737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1608af49b5814b7dbe02bdfb30312169fc5c5eda829449752a8c126b31374edc" } } ], "extra": [ 1, 43, 110, 17, 96, 50, 229, 159, 225, 238, 43, 250, 73, 62, 21, 238, 168, 84, 212, 253, 67, 37, 140, 3, 253, 68, 233, 200, 205, 212, 145, 141, 177, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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