Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f778cca2d3d39ef9d95631ac5c8ceaa14ebea8108e120a06e39bdc6fe3b03f1

Tx prefix hash: 9ba2c2eb1c9f8f54b6d8967521c04bb61325484fdd86568eb0f943a801813243
Tx public key: eab81d71b7d80ee5ad5147f258b8e24cfda421cbe4d6026157e7a3f2a4f870f9
Timestamp: 1699561311 Timestamp [UCT]: 2023-11-09 20:21:51 Age [y:d:h:m:s]: 01:360:13:44:33
Block: 888116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516595 RingCT/type: yes/0
Extra: 01eab81d71b7d80ee5ad5147f258b8e24cfda421cbe4d6026157e7a3f2a4f870f90211000000044b8f5122000000000000000000

1 output(s) for total of 0.700330464000 dcy

stealth address amount amount idx
00: 4525f5822f980ec5ff98e4fb44ead7b87cc1a5cd06c7d2e104ca9f9d240dfc0d 0.700330464000 1344035 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": 888126, "vin": [ { "gen": { "height": 888116 } } ], "vout": [ { "amount": 700330464, "target": { "key": "4525f5822f980ec5ff98e4fb44ead7b87cc1a5cd06c7d2e104ca9f9d240dfc0d" } } ], "extra": [ 1, 234, 184, 29, 113, 183, 216, 14, 229, 173, 81, 71, 242, 88, 184, 226, 76, 253, 164, 33, 203, 228, 214, 2, 97, 87, 231, 163, 242, 164, 248, 112, 249, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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