Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 261154d4966ecd347fa95cf656025e90bee502851b8553a994d91d0bf898b858

Tx prefix hash: d1e002bd559803a1b668b4df12668bdcff9bf4c955e098623b56870626b2b0eb
Tx public key: b266eab5e9c96938e83d1db850e1045b19d93600d43d8dc3b7549a549637be7d
Timestamp: 1659200040 Timestamp [UCT]: 2022-07-30 16:54:00 Age [y:d:h:m:s]: 02:199:02:00:25
Block: 555093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 663468 RingCT/type: yes/0
Extra: 01b266eab5e9c96938e83d1db850e1045b19d93600d43d8dc3b7549a549637be7d021100000009ea8cbb85000000000000000000

1 output(s) for total of 8.886824133000 dcy

stealth address amount amount idx
00: 5d6c4e3cc949d17dff99064b6ce4e3a599f099d12a572ec864f804ba07953156 8.886824133000 986975 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": 555103, "vin": [ { "gen": { "height": 555093 } } ], "vout": [ { "amount": 8886824133, "target": { "key": "5d6c4e3cc949d17dff99064b6ce4e3a599f099d12a572ec864f804ba07953156" } } ], "extra": [ 1, 178, 102, 234, 181, 233, 201, 105, 56, 232, 61, 29, 184, 80, 225, 4, 91, 25, 217, 54, 0, 212, 61, 141, 195, 183, 84, 154, 84, 150, 55, 190, 125, 2, 17, 0, 0, 0, 9, 234, 140, 187, 133, 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