Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0733c710da84b17860515b24c32b37cee607e069fe6b9b5532082c6cdbe363f

Tx prefix hash: 21bf2efd9079b72ee734f53f1e87a4a6030d5af5766d99aa5761bfde87dbb082
Tx public key: 02409c785f9e99d642fb5c79f37033739e2febdc9e7ea94b3e8505455a78eb72
Timestamp: 1727788604 Timestamp [UCT]: 2024-10-01 13:16:44 Age [y:d:h:m:s]: 00:188:22:05:58
Block: 1122133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134812 RingCT/type: yes/0
Extra: 0102409c785f9e99d642fb5c79f37033739e2febdc9e7ea94b3e8505455a78eb7202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2db13d9d521d138f7a4c171753866f9a1b1bbb89a4f9856378ff8ac87ae7bd44 0.600000000000 1604520 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": 1122143, "vin": [ { "gen": { "height": 1122133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2db13d9d521d138f7a4c171753866f9a1b1bbb89a4f9856378ff8ac87ae7bd44" } } ], "extra": [ 1, 2, 64, 156, 120, 95, 158, 153, 214, 66, 251, 92, 121, 243, 112, 51, 115, 158, 47, 235, 220, 158, 126, 169, 75, 62, 133, 5, 69, 90, 120, 235, 114, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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