Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d46b7c403bf7756cc03b3deddb5e590b3436760ede81ad6434ae321b5c4f748

Tx prefix hash: 990d10522f13412a1d83b470e85770421f307ba7f3f3f4d6e4d80751bdb92219
Tx public key: 83c5896e6d2baa315680dcbde4a9dfedd4349b416df8b4837b6aaabe1f8d7ce4
Timestamp: 1681205266 Timestamp [UCT]: 2023-04-11 09:27:46 Age [y:d:h:m:s]: 01:274:13:24:17
Block: 736169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457742 RingCT/type: yes/0
Extra: 0183c5896e6d2baa315680dcbde4a9dfedd4349b416df8b4837b6aaabe1f8d7ce4021100000005b3164c24000000000000000000

1 output(s) for total of 2.232372830000 dcy

stealth address amount amount idx
00: b1cec385d5094514e65b91ae1f29a28cb4bf31739a8ae5794400831a2fcca400 2.232372830000 1182574 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": 736179, "vin": [ { "gen": { "height": 736169 } } ], "vout": [ { "amount": 2232372830, "target": { "key": "b1cec385d5094514e65b91ae1f29a28cb4bf31739a8ae5794400831a2fcca400" } } ], "extra": [ 1, 131, 197, 137, 110, 109, 43, 170, 49, 86, 128, 220, 189, 228, 169, 223, 237, 212, 52, 155, 65, 109, 248, 180, 131, 123, 106, 170, 190, 31, 141, 124, 228, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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