Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95afbe820c468b786b8baa6e198463bc5822082d5dc8a5b60cdd8d0d3170b91

Tx prefix hash: 88e89083bb36a0e6bfca67054c1511e8ed96c8a384b1ab933a200cbdd1e9954d
Tx public key: 9a6c2cd1dadc82a075381fb31fd1ec8c074601ee8eb118d485d54cde2d41c10a
Timestamp: 1703349611 Timestamp [UCT]: 2023-12-23 16:40:11 Age [y:d:h:m:s]: 01:116:16:24:57
Block: 919516 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344521 RingCT/type: yes/0
Extra: 019a6c2cd1dadc82a075381fb31fd1ec8c074601ee8eb118d485d54cde2d41c10a02110000001352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 444fc1455b6d9630e8696c5bd786582dce5b73da3b68a7436d9e8e9944642542 0.600000000000 1377190 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": 919526, "vin": [ { "gen": { "height": 919516 } } ], "vout": [ { "amount": 600000000, "target": { "key": "444fc1455b6d9630e8696c5bd786582dce5b73da3b68a7436d9e8e9944642542" } } ], "extra": [ 1, 154, 108, 44, 209, 218, 220, 130, 160, 117, 56, 31, 179, 31, 209, 236, 140, 7, 70, 1, 238, 142, 177, 24, 212, 133, 213, 76, 222, 45, 65, 193, 10, 2, 17, 0, 0, 0, 19, 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