Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d841cfb7a10b1415a85e7622d94ee6ba2879671efa7c5bf3daa605b49678215a

Tx prefix hash: 9b23c0b0b83414849a2d04f74466d845e8cbc77129946cbe5db35a5aacabf36d
Tx public key: f22cad734f2a1c4af4758089034b06a513244f90e310eb275a4381aedda73b2f
Timestamp: 1719440607 Timestamp [UCT]: 2024-06-26 22:23:27 Age [y:d:h:m:s]: 00:263:12:53:32
Block: 1052912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188326 RingCT/type: yes/0
Extra: 01f22cad734f2a1c4af4758089034b06a513244f90e310eb275a4381aedda73b2f02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b82c191dfd4154c30bda51a54f6f18d56fb6cf1b3bee43e69fd587c36c9cb14 0.600000000000 1523257 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": 1052922, "vin": [ { "gen": { "height": 1052912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b82c191dfd4154c30bda51a54f6f18d56fb6cf1b3bee43e69fd587c36c9cb14" } } ], "extra": [ 1, 242, 44, 173, 115, 79, 42, 28, 74, 244, 117, 128, 137, 3, 75, 6, 165, 19, 36, 79, 144, 227, 16, 235, 39, 90, 67, 129, 174, 221, 167, 59, 47, 2, 17, 0, 0, 0, 4, 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