Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f4e80d07b88b61e693fe352e2d2c33a5ba413cadfa49394942cf4a362c53f4e

Tx prefix hash: 10da9d59055529bf7d58333b1700560552cc866831767979dcb82d3483119e95
Tx public key: 7a30465624c0059ed750c37b27879b3d6b0c3e0ce5e5eba15a269e13c5bdf253
Timestamp: 1718542923 Timestamp [UCT]: 2024-06-16 13:02:03 Age [y:d:h:m:s]: 00:299:22:26:59
Block: 1045494 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214323 RingCT/type: yes/0
Extra: 017a30465624c0059ed750c37b27879b3d6b0c3e0ce5e5eba15a269e13c5bdf25302110000000f52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8bce17f3e171563c5b19237d1599075600cc4ea2767c2a21bc212f41569b15d 0.600000000000 1515081 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": 1045504, "vin": [ { "gen": { "height": 1045494 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8bce17f3e171563c5b19237d1599075600cc4ea2767c2a21bc212f41569b15d" } } ], "extra": [ 1, 122, 48, 70, 86, 36, 192, 5, 158, 215, 80, 195, 123, 39, 135, 155, 61, 107, 12, 62, 12, 229, 229, 235, 161, 90, 38, 158, 19, 197, 189, 242, 83, 2, 17, 0, 0, 0, 15, 82, 212, 126, 148, 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