Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c56a65e9d78cd129ae24281004376e293288daf2fce0989674ee10a8740c360a

Tx prefix hash: cf212acad1a09a0474c84c317ae47fbf4278e32007a3bc3015fc3f39c729a27d
Tx public key: 721f3bf6a5b54ddd2aa792d93dcb050d22f2a8cf7b77b2422034220d0d638d99
Timestamp: 1675230426 Timestamp [UCT]: 2023-02-01 05:47:06 Age [y:d:h:m:s]: 02:067:04:29:29
Block: 687270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 569641 RingCT/type: yes/0
Extra: 01721f3bf6a5b54ddd2aa792d93dcb050d22f2a8cf7b77b2422034220d0d638d990211000000015029cbac000000000000000000

1 output(s) for total of 3.241821682000 dcy

stealth address amount amount idx
00: 015223836870b7b2d6582673a9f373dd92109debe7564deabf75bbb7d83c9a6e 3.241821682000 1129826 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": 687280, "vin": [ { "gen": { "height": 687270 } } ], "vout": [ { "amount": 3241821682, "target": { "key": "015223836870b7b2d6582673a9f373dd92109debe7564deabf75bbb7d83c9a6e" } } ], "extra": [ 1, 114, 31, 59, 246, 165, 181, 77, 221, 42, 167, 146, 217, 61, 203, 5, 13, 34, 242, 168, 207, 123, 119, 178, 66, 32, 52, 34, 13, 13, 99, 141, 153, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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