Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be82abc265d0400ca417fd742ae07a61308adc78c0edc83f7b2a071ceb619bf5

Tx prefix hash: 8c27aca83febb5bb7016a9cfba163d9bcd9091647af5763c0a323387e1908a97
Tx public key: 8fd03f2539f4d82a09dad5d33639cafc124fa52a76b05774410cd5ce3c5a4f2a
Timestamp: 1707537242 Timestamp [UCT]: 2024-02-10 03:54:02 Age [y:d:h:m:s]: 01:091:13:20:24
Block: 954215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326515 RingCT/type: yes/0
Extra: 018fd03f2539f4d82a09dad5d33639cafc124fa52a76b05774410cd5ce3c5a4f2a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ccc33aa282e9a2a4218e94e1853563039e2bb05bcac99ee2b7a9be89263fd63 0.600000000000 1413491 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": 954225, "vin": [ { "gen": { "height": 954215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ccc33aa282e9a2a4218e94e1853563039e2bb05bcac99ee2b7a9be89263fd63" } } ], "extra": [ 1, 143, 208, 63, 37, 57, 244, 216, 42, 9, 218, 213, 211, 54, 57, 202, 252, 18, 79, 165, 42, 118, 176, 87, 116, 65, 12, 213, 206, 60, 90, 79, 42, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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