Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6332779ae2f64fa61690912e329a4ad57f0f43fb82d74d98a8ccc86ef9daf14a

Tx prefix hash: 60aa463a6143a2692eb84555123031e2555824e79e8ccfdcc401af2d3edc83f8
Tx public key: 923ff2b3160b7567c5fade468f7010f8e9891ca61f09e6ad53556d7261d90b8d
Timestamp: 1737869020 Timestamp [UCT]: 2025-01-26 05:23:40 Age [y:d:h:m:s]: 00:047:19:14:50
Block: 1205492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33991 RingCT/type: yes/0
Extra: 01923ff2b3160b7567c5fade468f7010f8e9891ca61f09e6ad53556d7261d90b8d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4acf818a8f5147dccc76c94d942fd418ad2f3ec85559cc230cfb1dc59f9b55a 0.600000000000 1692189 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": 1205502, "vin": [ { "gen": { "height": 1205492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4acf818a8f5147dccc76c94d942fd418ad2f3ec85559cc230cfb1dc59f9b55a" } } ], "extra": [ 1, 146, 63, 242, 179, 22, 11, 117, 103, 197, 250, 222, 70, 143, 112, 16, 248, 233, 137, 28, 166, 31, 9, 230, 173, 83, 85, 109, 114, 97, 217, 11, 141, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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