Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47330f2e021df2440c1e0c033ef32b744c08780df0e4919694dd8b710bbc8851

Tx prefix hash: 74595e9ed3df9fc78896bb1e6564b20ba50ea3f1f85de6ce3e14ff5b0a8d3e84
Tx public key: e1be85f41dc7b843ced0d9e3272c21eaa49c0e847b54eb28e20a983ff492d4f7
Timestamp: 1715577928 Timestamp [UCT]: 2024-05-13 05:25:28 Age [y:d:h:m:s]: 00:332:17:24:25
Block: 1020924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237796 RingCT/type: yes/0
Extra: 01e1be85f41dc7b843ced0d9e3272c21eaa49c0e847b54eb28e20a983ff492d4f7021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e71e1f5a92f3598ff74143375893ad3376274f86d5ea24d914de69ff5a1c68af 0.600000000000 1485055 of 15

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": 1020934, "vin": [ { "gen": { "height": 1020924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e71e1f5a92f3598ff74143375893ad3376274f86d5ea24d914de69ff5a1c68af" } } ], "extra": [ 1, 225, 190, 133, 244, 29, 199, 184, 67, 206, 208, 217, 227, 39, 44, 33, 234, 164, 156, 14, 132, 123, 84, 235, 40, 226, 10, 152, 63, 244, 146, 212, 247, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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