Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8375ea823675e0fb64309b2c62eb12e14ff3276f1cb318cbd73f017ee7ef31c9

Tx prefix hash: 0003d59c5c15c2da32008f1c793cd65ffee9738535a7e705d86290e34620f8a2
Tx public key: 74e34fbea2bbc9cb06da10bc9db197d9da0c289ef1b25bbfb9c28220981fbf53
Timestamp: 1732499726 Timestamp [UCT]: 2024-11-25 01:55:26 Age [y:d:h:m:s]: 00:144:04:02:42
Block: 1161080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102867 RingCT/type: yes/0
Extra: 0174e34fbea2bbc9cb06da10bc9db197d9da0c289ef1b25bbfb9c28220981fbf530211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1675717438b71987fa1a92a57d1c7bcd8fcf92dbcf040dbd6b30e1cd213f932c 0.600000000000 1646731 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": 1161090, "vin": [ { "gen": { "height": 1161080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1675717438b71987fa1a92a57d1c7bcd8fcf92dbcf040dbd6b30e1cd213f932c" } } ], "extra": [ 1, 116, 227, 79, 190, 162, 187, 201, 203, 6, 218, 16, 188, 157, 177, 151, 217, 218, 12, 40, 158, 241, 178, 91, 191, 185, 194, 130, 32, 152, 31, 191, 83, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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