Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 220b02be6d620bb2a35fc12c5cb5b24346a020f5c3e97c3a8212e4770edf229c

Tx prefix hash: 1132d2022fb54c46ef5460986c97f2d9030230cbae7efd3d558c8ee8abf26e9e
Tx public key: bc8bd0a060c5514e7eb32822cf0ac9757c6898ace151c8600a1f34f4ed16bc1c
Timestamp: 1581820666 Timestamp [UCT]: 2020-02-16 02:37:46 Age [y:d:h:m:s]: 05:259:05:55:55
Block: 65722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1336090 RingCT/type: yes/0
Extra: 01bc8bd0a060c5514e7eb32822cf0ac9757c6898ace151c8600a1f34f4ed16bc1c02110000000203d36d11000000000000000000

1 output(s) for total of 371.737643408000 dcy

stealth address amount amount idx
00: 5d064469744b367e578cde95c7653d430b1463498e7c8bf17bcdf424639cf7d2 371.737643408000 121291 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": 65732, "vin": [ { "gen": { "height": 65722 } } ], "vout": [ { "amount": 371737643408, "target": { "key": "5d064469744b367e578cde95c7653d430b1463498e7c8bf17bcdf424639cf7d2" } } ], "extra": [ 1, 188, 139, 208, 160, 96, 197, 81, 78, 126, 179, 40, 34, 207, 10, 201, 117, 124, 104, 152, 172, 225, 81, 200, 96, 10, 31, 52, 244, 237, 22, 188, 28, 2, 17, 0, 0, 0, 2, 3, 211, 109, 17, 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