Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435f1a09c5bcae48b4968bbc887d420fe42b6cd6b39ed0c12d66f110ea5930e7

Tx prefix hash: 64a989e7233ac33a3ecc801d7d866e4bfcbb5b3352917e6e28217aedfcece86a
Tx public key: 1d1feb14b3501adf73e30090b10f19dda8b70ee77ffd50fa29af232edf02fdff
Timestamp: 1695554518 Timestamp [UCT]: 2023-09-24 11:21:58 Age [y:d:h:m:s]: 01:185:13:59:56
Block: 855090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393691 RingCT/type: yes/0
Extra: 011d1feb14b3501adf73e30090b10f19dda8b70ee77ffd50fa29af232edf02fdff021100000003faf35c9c000000000000000000

1 output(s) for total of 0.901014779000 dcy

stealth address amount amount idx
00: c876dad11fd3444349c58ba70e647e1fe8de6a503dbf1f4cbee9a1567053aa66 0.901014779000 1309092 of 0

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": 855100, "vin": [ { "gen": { "height": 855090 } } ], "vout": [ { "amount": 901014779, "target": { "key": "c876dad11fd3444349c58ba70e647e1fe8de6a503dbf1f4cbee9a1567053aa66" } } ], "extra": [ 1, 29, 31, 235, 20, 179, 80, 26, 223, 115, 227, 0, 144, 177, 15, 25, 221, 168, 183, 14, 231, 127, 253, 80, 250, 41, 175, 35, 46, 223, 2, 253, 255, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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