Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3f0a0964f3c3a71f4d8aecb22be0a8ec2a76e1e99ed8f1241622383df11a4a4

Tx prefix hash: a675c73a8c5b80c17102eafee51da5d9373af942eac8c30b1b7e6899166dcb80
Tx public key: 9de88371dde99ce37d56125440c3017cc9a608361313c71b1e80b76bd86a0914
Timestamp: 1712022853 Timestamp [UCT]: 2024-04-02 01:54:13 Age [y:d:h:m:s]: 01:264:01:31:30
Block: 991389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447491 RingCT/type: yes/0
Extra: 019de88371dde99ce37d56125440c3017cc9a608361313c71b1e80b76bd86a091402110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1acea88251d1e0bb0010fdc429cea1e36452bb54fa9f4b41fe58692939fca73c 0.600000000000 1451723 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": 991399, "vin": [ { "gen": { "height": 991389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1acea88251d1e0bb0010fdc429cea1e36452bb54fa9f4b41fe58692939fca73c" } } ], "extra": [ 1, 157, 232, 131, 113, 221, 233, 156, 227, 125, 86, 18, 84, 64, 195, 1, 124, 201, 166, 8, 54, 19, 19, 199, 27, 30, 128, 183, 107, 216, 106, 9, 20, 2, 17, 0, 0, 0, 12, 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