Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2e6937ebef0981ab8c10d10c621a34ddf1d9062743aa2304783baf419eabb93

Tx prefix hash: 2135e8e1114c4e0d2e585daeee920b8204f500ac03dcf3c731bb505973a67e4e
Tx public key: f01e9e73fb79d0b4178d4c0683dcb7610fe8c6d9e1d6122b918d25bc87b5c1cc
Timestamp: 1709906827 Timestamp [UCT]: 2024-03-08 14:07:07 Age [y:d:h:m:s]: 01:244:17:08:51
Block: 973889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433598 RingCT/type: yes/0
Extra: 01f01e9e73fb79d0b4178d4c0683dcb7610fe8c6d9e1d6122b918d25bc87b5c1cc02110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eaae437aef56e89ba94db96c18fa70a442fa416c38189be64d611b862f8cc4a2 0.600000000000 1433832 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": 973899, "vin": [ { "gen": { "height": 973889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eaae437aef56e89ba94db96c18fa70a442fa416c38189be64d611b862f8cc4a2" } } ], "extra": [ 1, 240, 30, 158, 115, 251, 121, 208, 180, 23, 141, 76, 6, 131, 220, 183, 97, 15, 232, 198, 217, 225, 214, 18, 43, 145, 141, 37, 188, 135, 181, 193, 204, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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