Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff8f4c98c10f59cd9ed5fee77bd58c35636c20e66f8f2d3b8635de812aff70e

Tx prefix hash: 044d935cea5094b6433e816dd6555423ea1152745199b23d9b17f1ce2e4e2c42
Tx public key: de6d0a5bf8d5c30a4a281c33c87e46135534658ae01704056353de727f024f2b
Timestamp: 1722747780 Timestamp [UCT]: 2024-08-04 05:03:00 Age [y:d:h:m:s]: 00:290:22:08:43
Block: 1080334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207864 RingCT/type: yes/0
Extra: 01de6d0a5bf8d5c30a4a281c33c87e46135534658ae01704056353de727f024f2b02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cef73ee3db2bcd5cf52d58444b71660883c36fc613d5e962365b08c03078ed38 0.600000000000 1553645 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": 1080344, "vin": [ { "gen": { "height": 1080334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cef73ee3db2bcd5cf52d58444b71660883c36fc613d5e962365b08c03078ed38" } } ], "extra": [ 1, 222, 109, 10, 91, 248, 213, 195, 10, 74, 40, 28, 51, 200, 126, 70, 19, 85, 52, 101, 138, 224, 23, 4, 5, 99, 83, 222, 114, 127, 2, 79, 43, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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