Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4264374b94868c819a395fc90c61a463db89aae26722b83de128ffa331d1807

Tx prefix hash: bea84403a3d016c8c5f4ab3bc4cbc4bed39338cd7b03d6160e41e96706a5cec7
Tx public key: 75cfffb2b0bd5ae2d6a9a472461eea942d026fcb49f3e5d4a0660f8f8e179c98
Timestamp: 1720669918 Timestamp [UCT]: 2024-07-11 03:51:58 Age [y:d:h:m:s]: 00:279:07:12:15
Block: 1063115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199552 RingCT/type: yes/0
Extra: 0175cfffb2b0bd5ae2d6a9a472461eea942d026fcb49f3e5d4a0660f8f8e179c9802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ad9deb144a69d84bcad50c6ad962af68efa40618287032844870d6db6b38f95 0.600000000000 1533628 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": 1063125, "vin": [ { "gen": { "height": 1063115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ad9deb144a69d84bcad50c6ad962af68efa40618287032844870d6db6b38f95" } } ], "extra": [ 1, 117, 207, 255, 178, 176, 189, 90, 226, 214, 169, 164, 114, 70, 30, 234, 148, 45, 2, 111, 203, 73, 243, 229, 212, 160, 102, 15, 143, 142, 23, 156, 152, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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