Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26816f4e0cf0db164c48ebf1c104ef9ef48ff74504502562d435d0bbcd7952db

Tx prefix hash: f51ca114dd7c9b31e660751086c1a6ce6203b961bb7023fc7329b7e652ca6292
Tx public key: 0a69c941b6cee3b6c6b4e3927fbee1b3c996ce5b057ef54df434d112ad308fea
Timestamp: 1705839851 Timestamp [UCT]: 2024-01-21 12:24:11 Age [y:d:h:m:s]: 01:146:14:12:38
Block: 940127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365825 RingCT/type: yes/0
Extra: 010a69c941b6cee3b6c6b4e3927fbee1b3c996ce5b057ef54df434d112ad308fea02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dd531c619f3086cec90cc26e2839796e74a2cdd573dbd379701f547d7f3cb87 0.600000000000 1398261 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": 940137, "vin": [ { "gen": { "height": 940127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dd531c619f3086cec90cc26e2839796e74a2cdd573dbd379701f547d7f3cb87" } } ], "extra": [ 1, 10, 105, 201, 65, 182, 206, 227, 182, 198, 180, 227, 146, 127, 190, 225, 179, 201, 150, 206, 91, 5, 126, 245, 77, 244, 52, 209, 18, 173, 48, 143, 234, 2, 17, 0, 0, 0, 2, 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