Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c8e5dd4ad3caa2c967b1cfb8fcdf3567777a06fd2738adba15197ff74161a12

Tx prefix hash: 7f595e05aca2900f377cd5e620a08dad52423bda6674d3cbcac9ae4e0f313046
Tx public key: eb634f4769916cb832b9cde513f36aa3b4e99dcccd2431b9c03f0746da5ed15b
Timestamp: 1710680518 Timestamp [UCT]: 2024-03-17 13:01:58 Age [y:d:h:m:s]: 00:187:17:24:42
Block: 980311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134454 RingCT/type: yes/0
Extra: 01eb634f4769916cb832b9cde513f36aa3b4e99dcccd2431b9c03f0746da5ed15b02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f529555418673651bf50c548b4c0d3572f19c36e82f6414f9d19d8cabbe56d9 0.600000000000 1440376 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": 980321, "vin": [ { "gen": { "height": 980311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f529555418673651bf50c548b4c0d3572f19c36e82f6414f9d19d8cabbe56d9" } } ], "extra": [ 1, 235, 99, 79, 71, 105, 145, 108, 184, 50, 185, 205, 229, 19, 243, 106, 163, 180, 233, 157, 204, 205, 36, 49, 185, 192, 63, 7, 70, 218, 94, 209, 91, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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