Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cd57e78709f383856bcfe69c08fe91663db3b94b668dc3d2ed78e3798cada63

Tx prefix hash: b2ba286fa41d26636d9d8dd15f1a66845d31a550b158def5a0ee940d9b13702f
Tx public key: e1e3419a7ed585db7733c0714a691f00a93f41f917627e0e01f5a7f9ad94c730
Timestamp: 1703326211 Timestamp [UCT]: 2023-12-23 10:10:11 Age [y:d:h:m:s]: 01:348:01:59:07
Block: 919320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507663 RingCT/type: yes/0
Extra: 01e1e3419a7ed585db7733c0714a691f00a93f41f917627e0e01f5a7f9ad94c7300211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad25dd8dd840d86c75397327ee23d85a895aca75effbf9dc91d9b74f8188cb15 0.600000000000 1376990 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": 919330, "vin": [ { "gen": { "height": 919320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad25dd8dd840d86c75397327ee23d85a895aca75effbf9dc91d9b74f8188cb15" } } ], "extra": [ 1, 225, 227, 65, 154, 126, 213, 133, 219, 119, 51, 192, 113, 74, 105, 31, 0, 169, 63, 65, 249, 23, 98, 126, 14, 1, 245, 167, 249, 173, 148, 199, 48, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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