Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cd87ce15c98ca70aac20ee23737ae939fa744066b16baccdd5867cfb77389b5

Tx prefix hash: 11c21dcf19bbf8820cf0243ad4cb8d9d32050cdddac39f2c8e3e89ef17c82c15
Tx public key: aa7481cbdee1e869c36c61d9d49e79bb39cca6f77c3e727d50bb6add0c4a3b10
Timestamp: 1752323104 Timestamp [UCT]: 2025-07-12 12:25:04 Age [y:d:h:m:s]: 00:131:16:01:51
Block: 1323898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92802 RingCT/type: yes/0
Extra: 01aa7481cbdee1e869c36c61d9d49e79bb39cca6f77c3e727d50bb6add0c4a3b100211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a586441e8d1f6b980d32236030712ace1f0e1a64b14a4486117016a7e9146ba3 0.600000000000 1811639 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": 1323908, "vin": [ { "gen": { "height": 1323898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a586441e8d1f6b980d32236030712ace1f0e1a64b14a4486117016a7e9146ba3" } } ], "extra": [ 1, 170, 116, 129, 203, 222, 225, 232, 105, 195, 108, 97, 217, 212, 158, 121, 187, 57, 204, 166, 247, 124, 62, 114, 125, 80, 187, 106, 221, 12, 74, 59, 16, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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