Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e86edf39a46b3215be1328d0aaba67ac29d704408d317c7ce47ad2c5b3a5d593

Tx prefix hash: 4edc984166e634c5f5a2a2a37601e404b4fb418828d4fc73fbed137d116de0d8
Tx public key: 7666e0b6138556505f56ec0afe77dc42f350101e1d7fddc305fa7367e3df717f
Timestamp: 1709879021 Timestamp [UCT]: 2024-03-08 06:23:41 Age [y:d:h:m:s]: 01:247:02:39:53
Block: 973653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435325 RingCT/type: yes/0
Extra: 017666e0b6138556505f56ec0afe77dc42f350101e1d7fddc305fa7367e3df717f02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b138789e327becee092abb2d36e908628c04b2de1f92042b62c42bc3e22297b 0.600000000000 1433588 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": 973663, "vin": [ { "gen": { "height": 973653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b138789e327becee092abb2d36e908628c04b2de1f92042b62c42bc3e22297b" } } ], "extra": [ 1, 118, 102, 224, 182, 19, 133, 86, 80, 95, 86, 236, 10, 254, 119, 220, 66, 243, 80, 16, 30, 29, 127, 221, 195, 5, 250, 115, 103, 227, 223, 113, 127, 2, 17, 0, 0, 0, 3, 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