Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d5500f1133f287710c41cf332db8ec2cf0ad6dcb07b19ce252edbba82e87e14

Tx prefix hash: aec6399611363a7f5939e549b9dfeee1e86f636c9a2cc8baa039959ea0930ec8
Tx public key: 50079edabde2558fdd51a1c82d1e9621b05deb428fcfc92e5747af49313eb25c
Timestamp: 1589362494 Timestamp [UCT]: 2020-05-13 09:34:54 Age [y:d:h:m:s]: 04:177:20:02:25
Block: 100400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1047197 RingCT/type: yes/0
Extra: 0150079edabde2558fdd51a1c82d1e9621b05deb428fcfc92e5747af49313eb25c02110000018437fb5df4000000000000000000

1 output(s) for total of 285.321095801000 dcy

stealth address amount amount idx
00: bc7389a3e5d07d3242312a01a63a9f9f5b3de210049dd3b14635fe0af2c2a062 285.321095801000 176916 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": 100410, "vin": [ { "gen": { "height": 100400 } } ], "vout": [ { "amount": 285321095801, "target": { "key": "bc7389a3e5d07d3242312a01a63a9f9f5b3de210049dd3b14635fe0af2c2a062" } } ], "extra": [ 1, 80, 7, 158, 218, 189, 226, 85, 143, 221, 81, 161, 200, 45, 30, 150, 33, 176, 93, 235, 66, 143, 207, 201, 46, 87, 71, 175, 73, 49, 62, 178, 92, 2, 17, 0, 0, 1, 132, 55, 251, 93, 244, 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