Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f392da716b670fd6a5c5eca490e0370d123fbf6cc2efa50fd9b9c4694d0040e

Tx prefix hash: 9c97d80adcbdae1bd63e1ee90386f5482ef3edb7aa1b22f0c2a0d2e4943fa8b1
Tx public key: af79c20715d5e7f6e2100488f7c6f48eed1669ee05a3612920148192bd0abe79
Timestamp: 1677864353 Timestamp [UCT]: 2023-03-03 17:25:53 Age [y:d:h:m:s]: 01:325:22:33:47
Block: 709116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493834 RingCT/type: yes/0
Extra: 01af79c20715d5e7f6e2100488f7c6f48eed1669ee05a3612920148192bd0abe790211000000015029cbac000000000000000000

1 output(s) for total of 2.744127107000 dcy

stealth address amount amount idx
00: a04e934541ec23b87e4c7a018e2eb8f014e879f8ea1319e3f217083ee7cef365 2.744127107000 1153069 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": 709126, "vin": [ { "gen": { "height": 709116 } } ], "vout": [ { "amount": 2744127107, "target": { "key": "a04e934541ec23b87e4c7a018e2eb8f014e879f8ea1319e3f217083ee7cef365" } } ], "extra": [ 1, 175, 121, 194, 7, 21, 213, 231, 246, 226, 16, 4, 136, 247, 198, 244, 142, 237, 22, 105, 238, 5, 163, 97, 41, 32, 20, 129, 146, 189, 10, 190, 121, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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