Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf77ca5275ab0e682f3844bffcbf57ca53805c1daf9fde4edaa9ee4f88accb1

Tx prefix hash: ff79df385995e94718c04633fae679b5c165e45070030dd9333f2193c29fc0bb
Tx public key: f86a897893e54ab17cd6d8e6a42a8238040254a083afd45dff20e136212029d3
Timestamp: 1696603845 Timestamp [UCT]: 2023-10-06 14:50:45 Age [y:d:h:m:s]: 01:098:03:51:44
Block: 863788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331418 RingCT/type: yes/0
Extra: 01f86a897893e54ab17cd6d8e6a42a8238040254a083afd45dff20e136212029d3021100000001faf35c9c000000000000000000

1 output(s) for total of 0.843213537000 dcy

stealth address amount amount idx
00: f7a40ebb341d51100dc537b07eafb8bc8266b712a1c78e9dc8d7b458fa1271f1 0.843213537000 1318278 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": 863798, "vin": [ { "gen": { "height": 863788 } } ], "vout": [ { "amount": 843213537, "target": { "key": "f7a40ebb341d51100dc537b07eafb8bc8266b712a1c78e9dc8d7b458fa1271f1" } } ], "extra": [ 1, 248, 106, 137, 120, 147, 229, 74, 177, 124, 214, 216, 230, 164, 42, 130, 56, 4, 2, 84, 160, 131, 175, 212, 93, 255, 32, 225, 54, 33, 32, 41, 211, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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