Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2367131279098e86bc3b1a2130b0f0a9816f76ffba6c4c4c5af1db7d318ff136

Tx prefix hash: bdda210dcb909ec3d312122792a59ecee06a08c6e15b5db077cae4957c034ba2
Tx public key: 99871edd6c55c50cb7dbd875d6eba4fb0b54d3382302ac4b894688de18935342
Timestamp: 1721956617 Timestamp [UCT]: 2024-07-26 01:16:57 Age [y:d:h:m:s]: 00:330:08:41:44
Block: 1073772 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235905 RingCT/type: yes/0
Extra: 0199871edd6c55c50cb7dbd875d6eba4fb0b54d3382302ac4b894688de18935342021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 535e66d121f82bc4fd5704da250dee28e9a1df22eef0f2c3d083abb36071e4ef 0.600000000000 1546279 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": 1073782, "vin": [ { "gen": { "height": 1073772 } } ], "vout": [ { "amount": 600000000, "target": { "key": "535e66d121f82bc4fd5704da250dee28e9a1df22eef0f2c3d083abb36071e4ef" } } ], "extra": [ 1, 153, 135, 30, 221, 108, 85, 197, 12, 183, 219, 216, 117, 214, 235, 164, 251, 11, 84, 211, 56, 35, 2, 172, 75, 137, 70, 136, 222, 24, 147, 83, 66, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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