Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a62120b9e5d517c7688443e1aa9a9294f03e929cda496502c35dbdcda2061501

Tx prefix hash: 81c199c887597a0df86980ea8975abee8562b96f28e2176cebce6513d01fd477
Tx public key: 873c9adaf3d4d56518814c7f34e781a939c92a258cf1fc9e5719d562f489b32f
Timestamp: 1673941780 Timestamp [UCT]: 2023-01-17 07:49:40 Age [y:d:h:m:s]: 02:012:16:18:33
Block: 676569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530709 RingCT/type: yes/0
Extra: 01873c9adaf3d4d56518814c7f34e781a939c92a258cf1fc9e5719d562f489b32f0211000000018b7b6602000000000000000000

1 output(s) for total of 3.517596281000 dcy

stealth address amount amount idx
00: a9666dc4e9e8636f4844868be6ffa2fbbbc0cfce99f387a20a92aa14fcb633de 3.517596281000 1118290 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": 676579, "vin": [ { "gen": { "height": 676569 } } ], "vout": [ { "amount": 3517596281, "target": { "key": "a9666dc4e9e8636f4844868be6ffa2fbbbc0cfce99f387a20a92aa14fcb633de" } } ], "extra": [ 1, 135, 60, 154, 218, 243, 212, 213, 101, 24, 129, 76, 127, 52, 231, 129, 169, 57, 201, 42, 37, 140, 241, 252, 158, 87, 25, 213, 98, 244, 137, 179, 47, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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