Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7236caad376633f8516fa9077e9842c3e734940c556ea856b093825d979649c

Tx prefix hash: 4e81b632a89a693ab8a5a23a737f85ffdd0b069234c3df25be3b7d4630151a64
Tx public key: 4cbb8169157352d162ad80c9a36a5e9937377cf4fd2a2f167e0ec11a329c8595
Timestamp: 1751006735 Timestamp [UCT]: 2025-06-27 06:45:35 Age [y:d:h:m:s]: 00:140:04:00:47
Block: 1313699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98194 RingCT/type: yes/0
Extra: 014cbb8169157352d162ad80c9a36a5e9937377cf4fd2a2f167e0ec11a329c859502110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e0c81435ad77095f511ca4defc4fd8a4f7a6745f056d0e64c997ce43111b57e 0.600000000000 1801342 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": 1313709, "vin": [ { "gen": { "height": 1313699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e0c81435ad77095f511ca4defc4fd8a4f7a6745f056d0e64c997ce43111b57e" } } ], "extra": [ 1, 76, 187, 129, 105, 21, 115, 82, 209, 98, 173, 128, 201, 163, 106, 94, 153, 55, 55, 124, 244, 253, 42, 47, 22, 126, 14, 193, 26, 50, 156, 133, 149, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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