Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bb2d9542edd21790914d56d6227b68b2cbdfb8336aa4d3062a5100798b1f324

Tx prefix hash: 6d50f676747b8455996e140110cb965e2f3c9206d8f658ebcc3f55e4c0176810
Tx public key: 54c53d79e7b3b6b84508111d4ff7b6f4c7a5c863c1ee1959c15103699c10592b
Timestamp: 1709332872 Timestamp [UCT]: 2024-03-01 22:41:12 Age [y:d:h:m:s]: 01:041:01:46:40
Block: 969129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290361 RingCT/type: yes/0
Extra: 0154c53d79e7b3b6b84508111d4ff7b6f4c7a5c863c1ee1959c15103699c10592b0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 926603a2c43444359eb1fa15fe623412e51d015193e48bd8e1f90cbdd469b0ff 0.600000000000 1428956 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": 969139, "vin": [ { "gen": { "height": 969129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "926603a2c43444359eb1fa15fe623412e51d015193e48bd8e1f90cbdd469b0ff" } } ], "extra": [ 1, 84, 197, 61, 121, 231, 179, 182, 184, 69, 8, 17, 29, 79, 247, 182, 244, 199, 165, 200, 99, 193, 238, 25, 89, 193, 81, 3, 105, 156, 16, 89, 43, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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