Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40842c5110234ea8b02da036d66c743ae710d241d5e962ae0f9efdccd07d85c7

Tx prefix hash: dac36be041b6704350d8e9464aba193dc84d1aca0c80b8615d1fcc16bdd044c7
Tx public key: 8c1b0bfe1204eeb8770dfaf9c8e55ffdfbb1974d91bd5e0288323db6481ec4bb
Timestamp: 1726199883 Timestamp [UCT]: 2024-09-13 03:58:03 Age [y:d:h:m:s]: 00:008:19:26:24
Block: 1108949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6317 RingCT/type: yes/0
Extra: 018c1b0bfe1204eeb8770dfaf9c8e55ffdfbb1974d91bd5e0288323db6481ec4bb021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7e83d65f54206ba7370aa006c594d4ca8d6332239d4708625905c871787ce65 0.600000000000 1587032 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": 1108959, "vin": [ { "gen": { "height": 1108949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7e83d65f54206ba7370aa006c594d4ca8d6332239d4708625905c871787ce65" } } ], "extra": [ 1, 140, 27, 11, 254, 18, 4, 238, 184, 119, 13, 250, 249, 200, 229, 95, 253, 251, 177, 151, 77, 145, 189, 94, 2, 136, 50, 61, 182, 72, 30, 196, 187, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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