Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91019a037b75ef587b753995595fa68646c00a08b5ea4427b0eb5941adf7ec7d

Tx prefix hash: d9ad20d6e8a157e4b860271175ed968d26f7bc2106a48c84672126a0ad42c6b4
Tx public key: 4f98bce34d67b863e7f0e94032d8855d0aec795ff7facef3a4ca4da2f2210e11
Timestamp: 1718158326 Timestamp [UCT]: 2024-06-12 02:12:06 Age [y:d:h:m:s]: 00:292:08:05:23
Block: 1042293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208901 RingCT/type: yes/0
Extra: 014f98bce34d67b863e7f0e94032d8855d0aec795ff7facef3a4ca4da2f2210e1102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab6ff6aa11a222d289cf394313a5804f60ea2bc34c48196849ec4d11f66aaea3 0.600000000000 1511176 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": 1042303, "vin": [ { "gen": { "height": 1042293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab6ff6aa11a222d289cf394313a5804f60ea2bc34c48196849ec4d11f66aaea3" } } ], "extra": [ 1, 79, 152, 188, 227, 77, 103, 184, 99, 231, 240, 233, 64, 50, 216, 133, 93, 10, 236, 121, 95, 247, 250, 206, 243, 164, 202, 77, 162, 242, 33, 14, 17, 2, 17, 0, 0, 0, 1, 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