Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18f3369a04f3f83b3079b8339c20ab70baa55cdb3f4c5a2c2dbc9467c5fc04fc

Tx prefix hash: 3592369c7da792648cffe4c2be0757248a3d61d1acf2f6ab473ba1de62a7c306
Tx public key: 6a6cad2815a8196a81710f9bf61ac0645b2f25ce2a8b4f4dc4eadf4959959cfc
Timestamp: 1694259621 Timestamp [UCT]: 2023-09-09 11:40:21 Age [y:d:h:m:s]: 01:167:19:20:06
Block: 844330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380992 RingCT/type: yes/0
Extra: 016a6cad2815a8196a81710f9bf61ac0645b2f25ce2a8b4f4dc4eadf4959959cfc02110000000733af99f4000000000000000000

1 output(s) for total of 0.978102293000 dcy

stealth address amount amount idx
00: 0b6bc2d455c836c9ebc2ebfaaea5ddf64b1b5b22f31ba57af8fbeeb2bbb929eb 0.978102293000 1297632 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": 844340, "vin": [ { "gen": { "height": 844330 } } ], "vout": [ { "amount": 978102293, "target": { "key": "0b6bc2d455c836c9ebc2ebfaaea5ddf64b1b5b22f31ba57af8fbeeb2bbb929eb" } } ], "extra": [ 1, 106, 108, 173, 40, 21, 168, 25, 106, 129, 113, 15, 155, 246, 26, 192, 100, 91, 47, 37, 206, 42, 139, 79, 77, 196, 234, 223, 73, 89, 149, 156, 252, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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