Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d41c7a22fc9ae4a0b0d67b9b594227d994231383661037ca26976aa4ccfa0555

Tx prefix hash: a86da39c9a901004696994f6f7dfd0590914021d0ac6586c9a57536c7dbae162
Tx public key: e4e887a2d273edab63bcaf47c20c9ebe1c2009c6b13cb24cfe5e763cb1094292
Timestamp: 1715654134 Timestamp [UCT]: 2024-05-14 02:35:34 Age [y:d:h:m:s]: 00:330:02:01:08
Block: 1021523 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235935 RingCT/type: yes/0
Extra: 01e4e887a2d273edab63bcaf47c20c9ebe1c2009c6b13cb24cfe5e763cb10942920211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f4b7b71d2c63e3e90a110513a32514f0506060b0c148668a37eba6c32de656c 0.600000000000 1485868 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": 1021533, "vin": [ { "gen": { "height": 1021523 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f4b7b71d2c63e3e90a110513a32514f0506060b0c148668a37eba6c32de656c" } } ], "extra": [ 1, 228, 232, 135, 162, 210, 115, 237, 171, 99, 188, 175, 71, 194, 12, 158, 190, 28, 32, 9, 198, 177, 60, 178, 76, 254, 94, 118, 60, 177, 9, 66, 146, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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