Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c48db1b0a05c066cefd8df52fd08c850564abd7aed53842237815f3ad62c6f6

Tx prefix hash: 7231b2b3ecfd775cfae31dba3d34a7c34bd5cd9bea0a87e046a4e8f4a5272e0b
Tx public key: c222ba52a9b48822861521a7741e4d67916c7407f9526e956760ef40f1cd1961
Timestamp: 1709059357 Timestamp [UCT]: 2024-02-27 18:42:37 Age [y:d:h:m:s]: 01:001:14:34:43
Block: 966858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262120 RingCT/type: yes/0
Extra: 01c222ba52a9b48822861521a7741e4d67916c7407f9526e956760ef40f1cd19610211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5829cb24ad324e600d08fb096b7e1841690f9d62c265b7d46a137ef6669b4ce0 0.600000000000 1426629 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": 966868, "vin": [ { "gen": { "height": 966858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5829cb24ad324e600d08fb096b7e1841690f9d62c265b7d46a137ef6669b4ce0" } } ], "extra": [ 1, 194, 34, 186, 82, 169, 180, 136, 34, 134, 21, 33, 167, 116, 30, 77, 103, 145, 108, 116, 7, 249, 82, 110, 149, 103, 96, 239, 64, 241, 205, 25, 97, 2, 17, 0, 0, 0, 2, 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