Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd9858d634dee70eb50fb1ddeb498b602f47e1017d01a8ca0ec96d19a0dd3e5c

Tx prefix hash: 5296bb1190aafd70c0b595df71e2adbf6128a893e67a613499c5f64c4198bd69
Tx public key: 3aaf383d0b4a96341c326b0b549370f559d878d785861e5d11e5acbc62530470
Timestamp: 1649627155 Timestamp [UCT]: 2022-04-10 21:45:55 Age [y:d:h:m:s]: 03:036:12:53:16
Block: 477537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 806570 RingCT/type: yes/0
Extra: 013aaf383d0b4a96341c326b0b549370f559d878d785861e5d11e5acbc62530470021100000001a8c141c5000000000000000000

1 output(s) for total of 16.059126621000 dcy

stealth address amount amount idx
00: db48e4c4467a4e9b1b4f0eba4683a7e5aea5dde703f6725d2fd8006073ae0f9e 16.059126621000 898208 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": 477547, "vin": [ { "gen": { "height": 477537 } } ], "vout": [ { "amount": 16059126621, "target": { "key": "db48e4c4467a4e9b1b4f0eba4683a7e5aea5dde703f6725d2fd8006073ae0f9e" } } ], "extra": [ 1, 58, 175, 56, 61, 11, 74, 150, 52, 28, 50, 107, 11, 84, 147, 112, 245, 89, 216, 120, 215, 133, 134, 30, 93, 17, 229, 172, 188, 98, 83, 4, 112, 2, 17, 0, 0, 0, 1, 168, 193, 65, 197, 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