Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e3f3f348937194b131bf2d11063b67702558b95304464e2376d19f6b1ff195f0

Tx prefix hash: cb0b4c93bcc06ed153de18597598359d5968bd85b1a61f98f1839e45b5f37bff
Tx public key: 99f825e3da5fb5d370b6739b0d923d9f6abe20b467602218a3638558f2e95052
Timestamp: 1705812153 Timestamp [UCT]: 2024-01-21 04:42:33 Age [y:d:h:m:s]: 01:036:00:28:54
Block: 939893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286820 RingCT/type: yes/0
Extra: 0199f825e3da5fb5d370b6739b0d923d9f6abe20b467602218a3638558f2e9505202110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46baf527384fc8ff3fd559d2f8cb1a7ae5d5ed14b32d97970cc8022ee8a74354 0.600000000000 1398027 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": 939903, "vin": [ { "gen": { "height": 939893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46baf527384fc8ff3fd559d2f8cb1a7ae5d5ed14b32d97970cc8022ee8a74354" } } ], "extra": [ 1, 153, 248, 37, 227, 218, 95, 181, 211, 112, 182, 115, 155, 13, 146, 61, 159, 106, 190, 32, 180, 103, 96, 34, 24, 163, 99, 133, 88, 242, 233, 80, 82, 2, 17, 0, 0, 0, 11, 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