Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 502a141340892e616e1d3c97c9d8d20a36861200398b1686642202f2d60e4ddf

Tx prefix hash: f8228d2bcb69169af3d02fa99d83c6957f06a0bfc1f21edcf45adcf0b09266ca
Tx public key: e1e0a7ec0113dff67e9b7a867ba81b6078e5ef3a1db03895776b0bbce5df37a8
Timestamp: 1627589951 Timestamp [UCT]: 2021-07-29 20:19:11 Age [y:d:h:m:s]: 03:112:01:10:52
Block: 303382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 852573 RingCT/type: yes/0
Extra: 01e1e0a7ec0113dff67e9b7a867ba81b6078e5ef3a1db03895776b0bbce5df37a80211000000db282c04e2000000000000000000

1 output(s) for total of 60.642556202000 dcy

stealth address amount amount idx
00: 55208c48335f36605ac2e302377b960c313a8717ab170ca5c38a839479108913 60.642556202000 633225 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": 303392, "vin": [ { "gen": { "height": 303382 } } ], "vout": [ { "amount": 60642556202, "target": { "key": "55208c48335f36605ac2e302377b960c313a8717ab170ca5c38a839479108913" } } ], "extra": [ 1, 225, 224, 167, 236, 1, 19, 223, 246, 126, 155, 122, 134, 123, 168, 27, 96, 120, 229, 239, 58, 29, 176, 56, 149, 119, 107, 11, 188, 229, 223, 55, 168, 2, 17, 0, 0, 0, 219, 40, 44, 4, 226, 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