Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b867c0eec669eac2314a104edafc4fd97a8c79d71f09b7b535d6d590a51c13d

Tx prefix hash: 1d2bf4e9b110e304c6f8a985535659bbcf9f617c4207ca7f4cdadaac33f086c3
Tx public key: e386c9351c7cf25db65ec79cd390abda1e4c789df945355d70b58405905bee9e
Timestamp: 1704290613 Timestamp [UCT]: 2024-01-03 14:03:33 Age [y:d:h:m:s]: 01:129:19:24:53
Block: 927330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353885 RingCT/type: yes/0
Extra: 01e386c9351c7cf25db65ec79cd390abda1e4c789df945355d70b58405905bee9e021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa075dc3b706f3e9ba4035ccdbaa0e19875b63f6d80c2adce388a80d46c2b966 0.600000000000 1385166 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": 927340, "vin": [ { "gen": { "height": 927330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa075dc3b706f3e9ba4035ccdbaa0e19875b63f6d80c2adce388a80d46c2b966" } } ], "extra": [ 1, 227, 134, 201, 53, 28, 124, 242, 93, 182, 94, 199, 156, 211, 144, 171, 218, 30, 76, 120, 157, 249, 69, 53, 93, 112, 181, 132, 5, 144, 91, 238, 158, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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