Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 390f3f9e2eba29aed25cbe5e08c33d2e7723fd82aab7c0f3875a55542072096a

Tx prefix hash: 8098eb3bc84a8370a743d3f15db71d57db681ee34338ba5b65735191f62a58d8
Tx public key: 6dd2d07f0b0f549c8fd9b6e2d95001701e4887c5eed05622d10de7c0a37ad97e
Timestamp: 1702883602 Timestamp [UCT]: 2023-12-18 07:13:22 Age [y:d:h:m:s]: 01:110:02:01:12
Block: 915650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339803 RingCT/type: yes/0
Extra: 016dd2d07f0b0f549c8fd9b6e2d95001701e4887c5eed05622d10de7c0a37ad97e02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7b41dde5fad7caf4847f62b287ca74d0c249774ec93c14fac5ef16e6fc4927d 0.600000000000 1373046 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": 915660, "vin": [ { "gen": { "height": 915650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7b41dde5fad7caf4847f62b287ca74d0c249774ec93c14fac5ef16e6fc4927d" } } ], "extra": [ 1, 109, 210, 208, 127, 11, 15, 84, 156, 143, 217, 182, 226, 217, 80, 1, 112, 30, 72, 135, 197, 238, 208, 86, 34, 209, 13, 231, 192, 163, 122, 217, 126, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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