Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db0ee3506811ad58bd5da296573c4004db375ea9f42b7a5a09133ad1a767e742

Tx prefix hash: f0fde3ecee6f3a1dbaa6a886698f1b706d7b06a9aaac967ae24bd814aade31c9
Tx public key: fbb1a4349e23ecad3cd0496c791f85d28f62c086b70387a1475b22b621b32fba
Timestamp: 1711590602 Timestamp [UCT]: 2024-03-28 01:50:02 Age [y:d:h:m:s]: 01:050:00:56:33
Block: 987851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296744 RingCT/type: yes/0
Extra: 01fbb1a4349e23ecad3cd0496c791f85d28f62c086b70387a1475b22b621b32fba02110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e0af5ba593616513bf8733b6a0c3a0cb79b06bee6704e8fa93094bab73bdf6f 0.600000000000 1448112 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": 987861, "vin": [ { "gen": { "height": 987851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e0af5ba593616513bf8733b6a0c3a0cb79b06bee6704e8fa93094bab73bdf6f" } } ], "extra": [ 1, 251, 177, 164, 52, 158, 35, 236, 173, 60, 208, 73, 108, 121, 31, 133, 210, 143, 98, 192, 134, 183, 3, 135, 161, 71, 91, 34, 182, 33, 179, 47, 186, 2, 17, 0, 0, 0, 13, 82, 212, 126, 148, 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