Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6661e72121765b90ad139b774756c6fc60bc4ca3af0500545bf418e62bb5719

Tx prefix hash: a8defa0b80f3c0b323629407c63003ce4c7477ba0ebd9fa8e4034791447d690d
Tx public key: 3bcbad27b4bd26f3bcddae6cbc02e934710b7da7efa9d846f8a4ad01c55699b5
Timestamp: 1685000195 Timestamp [UCT]: 2023-05-25 07:36:35 Age [y:d:h:m:s]: 01:238:20:01:32
Block: 767643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432116 RingCT/type: yes/0
Extra: 013bcbad27b4bd26f3bcddae6cbc02e934710b7da7efa9d846f8a4ad01c55699b502110000000275e3f0e9000000000000000000

1 output(s) for total of 1.755821063000 dcy

stealth address amount amount idx
00: 50a38496a80f05629d5b18bb18101929b36a7cadbcf5650eb0e979f0c53f9d5c 1.755821063000 1216774 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": 767653, "vin": [ { "gen": { "height": 767643 } } ], "vout": [ { "amount": 1755821063, "target": { "key": "50a38496a80f05629d5b18bb18101929b36a7cadbcf5650eb0e979f0c53f9d5c" } } ], "extra": [ 1, 59, 203, 173, 39, 180, 189, 38, 243, 188, 221, 174, 108, 188, 2, 233, 52, 113, 11, 125, 167, 239, 169, 216, 70, 248, 164, 173, 1, 197, 86, 153, 181, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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